Skip to content

fix: add language specifiers to fenced code blocks#242

Merged
alex-solovyev merged 1 commit intomainfrom
chore/fix-markdownlint-errors
Jan 27, 2026
Merged

fix: add language specifiers to fenced code blocks#242
alex-solovyev merged 1 commit intomainfrom
chore/fix-markdownlint-errors

Conversation

@alex-solovyev
Copy link
Collaborator

@alex-solovyev alex-solovyev commented Jan 27, 2026

Summary

  • Add text language specifier to fenced code blocks that were missing language specification
  • Fixes MD040 markdownlint violations (fenced-code-language rule)

Changes

File Fix
.agent/tools/video/higgsfield.md Add text to dimension list and Context7 example
.agent/tools/video/remotion.md Add text to Context7 command example
.agent/tools/video/remotion/images.md Add text to directory structure
todo/PLANS.md Add text to pipeline flow and architecture diagrams
todo/tasks/prd-document-extraction.md Add text to architecture and pipeline diagrams

Testing

markdownlint-cli2 "**/*.md" --config .markdownlint.json 2>&1 | grep "\.md:" | grep -v "cloudflare-platform"
# Returns empty (no errors outside cloudflare-platform)

Note: 94 errors remain in .agent/services/hosting/cloudflare-platform/ - this is imported documentation that should be addressed separately or added to .markdownlintignore.

Summary by CodeRabbit

  • Documentation
    • Improved formatting and visual presentation of code blocks throughout video tool documentation and planning guides for enhanced readability.
    • Enhanced the display of code examples, integration sample queries, and ASCII architectural diagrams with better text formatting and structure.
    • Added sample integration paths, query examples, and comprehensive documentation details to provide clearer guidance for end users on tool capabilities.

✏️ Tip: You can customize this high-level summary in your review settings.

- higgsfield.md: add 'text' to dimension list and Context7 example
- remotion.md: add 'text' to Context7 command example
- remotion/images.md: add 'text' to directory structure
- PLANS.md: add 'text' to pipeline flow and architecture diagrams
- prd-document-extraction.md: add 'text' to architecture and pipeline diagrams

Fixes MD040 markdownlint violations (fenced-code-language rule)
@gemini-code-assist
Copy link

Summary of Changes

Hello @alex-solovyev, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request focuses on improving the quality and consistency of markdown documentation by addressing specific linting issues. It systematically adds language specifiers to code blocks that previously lacked them, ensuring adherence to markdown best practices and preventing future linting errors.

Highlights

  • Markdown Linting Fix: Added 'text' language specifiers to fenced code blocks across several markdown files to resolve MD040 markdownlint violations (fenced-code-language rule).
Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help /gemini help Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

@coderabbitai
Copy link
Contributor

coderabbitai bot commented Jan 27, 2026

Walkthrough

This PR updates documentation markdown files across the agent tools and planning directories, changing generic code fence delimiters to text-specific blocks (totext) for improved clarity. Additionally, sample documentation examples are appended to the Context7 integration sections and file structure ASCII diagrams are added. No functional code or API behavior changes.

Changes

Cohort / File(s) Summary
Video Agent Documentation
.agent/tools/video/higgsfield.md, .agent/tools/video/remotion.md, .agent/tools/video/remotion/images.md
Updated code fence delimiters from generic totext blocks. Added Context7 integration query examples in higgsfield.md (query-docs calls for text-to-image parameters, image-to-video models, character consistency). Added ASCII tree structure for public folder file references in remotion/images.md. Added sample path example "/context7 remotion [query]" in remotion.md.
Planning Documentation
todo/PLANS.md, todo/tasks/prd-document-extraction.md
Changed code fence delimiters from generic totext in pipeline flow and architecture diagram sections, preserving ASCII tree content while updating fence language specifications.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~4 minutes

Possibly related PRs

Poem

🪡 Code fences dressed in text attire,
Documentation climbing ever higher,
From generic marks to specified blocks,
Examples and diagrams unlock,
The guide shines bright, maintained with care! ✨

🚥 Pre-merge checks | ✅ 3
✅ Passed checks (3 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title accurately and concisely describes the main change: adding language specifiers to fenced code blocks to fix markdownlint violations.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.


Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

@augmentcode
Copy link

augmentcode bot commented Jan 27, 2026

🤖 Augment PR Summary

Summary: Adds explicit text language specifiers to previously untagged fenced code blocks across several docs.

Why: Resolves MD040 (fenced-code-language) markdownlint violations without changing the actual documented content.

🤖 Was this summary useful? React with 👍 or 👎

Copy link

@augmentcode augmentcode bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Review completed. No suggestions at this time.

Comment augment review to trigger a new review at any time.

@sonarqubecloud
Copy link

Copy link

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request addresses markdown linting violations by adding language specifiers to fenced code blocks across several documentation files. The changes are consistent and improve the overall quality and maintainability of the documentation. I've provided a couple of suggestions to use a more specific language specifier (shell instead of text) for code blocks representing command-line examples. This would provide better semantic meaning and potentially improve syntax highlighting. Overall, this is a valuable fix.

For up-to-date API documentation:

```
```text

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

For this code block, which appears to be a command-line example with a commented-out return value, using shell as the language specifier would be more descriptive than text. This would also allow syntax highlighters to correctly render the line starting with # as a comment, improving readability.

Suggested change
```text
```shell

For up-to-date API documentation:

```
```text

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

For this command example, using the shell language specifier is more semantic than text. It clearly indicates that this is a command to be run in a terminal environment.

Suggested change
```text
```shell

@github-actions
Copy link

🔍 Code Quality Report

�[0;35m[MONITOR]�[0m Code Review Monitoring Report

�[0;34m[INFO]�[0m Latest Quality Status:
SonarCloud: 0 bugs, 0 vulnerabilities, 457 code smells

�[0;34m[INFO]�[0m Recent monitoring activity:
Tue Jan 27 03:50:14 UTC 2026: Code review monitoring started
Tue Jan 27 03:50:14 UTC 2026: SonarCloud - Bugs: 0, Vulnerabilities: 0, Code Smells: 457
Tue Jan 27 03:50:14 UTC 2026: Qlty - 0 issues found, auto-formatting applied
Tue Jan 27 03:50:16 UTC 2026: Codacy analysis completed with auto-fixes

📈 Current Quality Metrics

  • BUGS: 0
  • CODE SMELLS: 457
  • VULNERABILITIES: 0

Generated on: Tue Jan 27 03:51:40 UTC 2026


Generated by AI DevOps Framework Code Review Monitoring

@alex-solovyev alex-solovyev merged commit fecbf58 into main Jan 27, 2026
17 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant